Scramnet Bug Fix	BKT 03-Aug-05

With the latest revision of Scramnet boards, the PCI autoconfiguration process failed because the Scramnet board reports that it needs more memory space than it has.

A complete description of the problem is as follows (from Dave Nelson):

The first problem ASD encountered was a failure of the processor to boot with a scramnet module installed on the processor.  After swapping various processors and scramnet PMCs it appears this problem is caused by a combination of newer scramnet hardware installed in a system where PCI auto-configuration is not successful.  ASD has resolved this issue by making a change to the RTOS telling it not to attempt the auto-configuration of the scramnet device.  This change allows the processor to successfully boot and since ASD software manually configures the scramnet module at runtime, the system functions as expected.  An effort is being made with the vendor Systran to determine why newer modules (unlike older modules) cause the processor the hang as it attempts to auto-configure the module.

The solution involves three steps: 

1) The boot rom must be modified.  Read "VxWorks Flash Programming RevA.doc" in the Documents folder to find out how to change the boot rom to the ROM image "asd2400boot.bin" or "asd5100boot.bin" in the bin folder, depending on the processor used.

2) The PCI bus must be manually configured by adding the following statements to "startp0.vxc" in the bin folder:

	/* manually the scramnet on the pci bus (because autoconfig crashes) */ 
	bus=0;
	dev=0;
	func=0;
	pciFindDevice(0x11b0, 0x4750, 0, &bus, &dev, &func);
	pciDevConfig(bus, dev, func, 0, 0xd0000000, 7);

   Note:  the "0xd0000000" is for 5100 PPCs; use "0x20000000" for 2400 PPCs.

3) Make sure to use the latest board support package (for superstition reasons).


